| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <link rel="icon" type="image/x-icon" href="/favicon.ico"> | |
| <title>Rebane's Discord Colored Text Generator</title> | |
| <meta charset="UTF-8"> | |
| <meta name="description" content="Rebane's Discord Colored Text Generator"> | |
| <meta name="author" content="rebane2001"> | |
| <meta content="#5865F2" name="theme-color"> | |
| <script id="discord:component-embed" type="application/json"> |
| // To reverse a string | |
| const reverseString = str => { | |
| let reversed = '' | |
| for (let i = str.length - 1; i >= 0; i--) reversed += str[i] | |
| return reversed | |
| } | |
| // To get vowels in a string | |
| const getVowels = str => { | |
| return str.match(/[aeiou]/gi)?.join('') || '' |
Here is the procedure formatted as clean, copy-pastable Markdown.
This procedure outlines how to create a bootable Windows 11 USB flash drive (or HDD/SSD) using the command line.
⚠️ WARNING: DATA LOSS This process involves formatting drives. Identify your device identifier correctly (e.g.,/dev/sdX). In the examples below, the device is/dev/sde. Do not copy/paste commands containing/dev/sdewithout verifying your specific drive identifier.
I recently got myself a Yubikey and wanted to set up the Yubico Authenticator with all the OTPs I had in Google Authenticator. Unfortunately Yubico Authenticator doesn't support scanning the QR-code that the Google Authenticator generates when you export the OTP-keys, and it seemed like quite the daunting task to log in to every service to generate new OTP-keys. So I decided to have a look at the contents of the QR code, to see if I could import the keys into Yubico Authenticator in one go. Luckily I found a blog post by Alex Bakker that describes the data format.
Unfortunately, but likely for the best, the security policy of Google Authenticator won't allow you to take a screenshot of
| Engine | Contact |
|---|---|
| 360 | kefu@360.cn |
| Abusix | support@abusix.com, https://lookup.abusix.com/ |
| Acronis | virustotal-falsepositive@acronis.com |
| ADMINUSLabs | info@adminuslabs.net, samples@adminus.net, falsepositive@adminuslabs.net |
| AegisLab | support@aegislab.com |
| Ahnlab | e-support@ahnlab.com, samples@ahnlab.com |
| AILabs (Monitorapp) | aicc@monitorapp.com |
| Alibaba | virustotal@list.alibaba-inc.com |
Ready-to-use disclosure badges and callouts for GitHub READMEs, based on the VisiData AI Contribution Levels.
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
[ Update 2025-03-24: Commenting is disabled permanently. Previous comments are archived at web.archive.org. ]
Most of the terminal emulators auto-detect when a URL appears onscreen and allow to conveniently open them (e.g. via Ctrl+click or Cmd+click, or the right click menu).
It was, however, not possible until now for arbitrary text to point to URLs, just as on webpages.
